Version Packages#400
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
a584668 to
b0150af
Compare
dferber90
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@flags-sdk/vercel@1.4.1
Patch Changes
b0150af]:flags@4.1.1
Patch Changes
50725a8Thanks @dferber90! - Recognize hanging promise rejection as internal Next.js error@vercel/flags-core@1.5.1
Patch Changes
#395
b0150afThanks @lucleray! - Reduce log noise from stream reconnects.Retryable stream errors are no longer logged on every failed attempt; the
underlying error is now surfaced only once retries are exhausted (via the
existing "Max retry count exceeded" log). The stream/polling initialization
timeout warnings were also reworded to make clear the client keeps connecting
in the background while serving fallback values.